Fix Incoming Documents default processed filter - #9401
Merged
Jesper Schulz-Wedde (JesperSchulz) merged 4 commits intoAug 17, 2026
Merged
Fix Incoming Documents default processed filter#9401Jesper Schulz-Wedde (JesperSchulz) merged 4 commits into
Jesper Schulz-Wedde (JesperSchulz) merged 4 commits into
Conversation
Restore the default unprocessed view while preserving explicit processed filters and add regression coverage for each filter scenario. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: a22e32be-3141-40ed-9a78-2302b3ba294f
Jesper Schulz-Wedde (JesperSchulz)
added
the
Team: Integrations
Contributor
Copilot PR ReviewIteration 4 · Outcome: completed
Knowledge source: https://github.com/microsoft/BCQuality@186d8a131465475c79244d994acb872cd5c0d4bf Orchestrator pre-filter (2 file(s) excluded)
Findings produced by the Copilot CLI agent against BCQuality at |
Darrick (darjoo)
previously approved these changes
Jul 14, 2026
Address review feedback by using the existing helper for the default unprocessed view. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: a22e32be-3141-40ed-9a78-2302b3ba294f
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Darrick (darjoo)
previously approved these changes
Jul 14, 2026
Only apply the default unprocessed filter when no Processed filter is supplied, preserving the intent of bug 609129. Cover the action state for filtered entry points. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: a22e32be-3141-40ed-9a78-2302b3ba294f
Clear and verify variable storage around the modal page handler so each filter scenario proves the expected interaction. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: a22e32be-3141-40ed-9a78-2302b3ba294f
Contributor
Author
|
Re-running CI. Something is off with the one last task which keeps failing. |
Jesper Schulz-Wedde (JesperSchulz)
temporarily deployed
to
triage
August 14, 2026 08:22 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
Darrick (darjoo)
approved these changes
Aug 17, 2026
Wenjie Fan (gggdttt)
approved these changes
Aug 17, 2026
Jesper Schulz-Wedde (JesperSchulz)
deleted the
jesperschulz-fix-incoming-documents-filter
branch
August 17, 2026 13:05
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
Incoming Documents no longer defaulted to unprocessed records when opened without a filter, and an explicit
Processed = truefilter could be cleared. Restore the defaultProcessed = falseview while preserving explicitly suppliedtrueandfalsefilters.Regression tests cover all three filter scenarios.
Linked work
Fixes AB#637747
How I validated this
What I tested and the outcome (required - be specific: scenarios, commands, screenshots for UI changes)
Processed = trueandProcessed = falsefilters are preserved.Risk & compatibility
Low risk. The change only affects initial page filter handling and retains existing Show All/Show Unprocessed action behavior. No data, permissions, or upgrade impact.